Skip to content

Development notes: replacing fixed constants with data-derived parameters - #5

Draft
agulaya24 wants to merge 2 commits into
mainfrom
docs/development-notes
Draft

Development notes: replacing fixed constants with data-derived parameters#5
agulaya24 wants to merge 2 commits into
mainfrom
docs/development-notes

Conversation

@agulaya24

Copy link
Copy Markdown
Owner

Adds docs/DEVELOPMENT_NOTES.md, a dated record of work in progress. One new file, no code changes.

What it says

The through-line is removing magic numbers by letting the data determine its own measurement parameters. That became necessary when running on large, dense personal corpora and when opening up organizational use cases, where constants that looked reasonable at small scale turned out to sit in the wrong part of the distribution. Nothing errored; the numbers stopped meaning what their names implied.

Most of the note is a defect report on our own code, published because a project that reports only what worked is not one whose measurements anyone should trust.

Covered, with numbers:

  • A distance conversion wrong for both ChromaDB spaces, which survived its own fix three times because one call site was missed each time, and which docs/core/ARCHITECTURE.md stated as fact. A doc that states a formula is where the next contributor learns to reimplement it.
  • A faithfulness guard set at 0.35 when randomly paired unrelated facts have a minimum similarity of 0.358 under the encoder in use, so it could never fire.
  • A deduplication step measured against gold labels at 83% correct when two facts genuinely are the same, and 23% when they are not.
  • What that merge behaviour revealed: it was detecting a real relation between two facts and had only destructive ways to record it, so it is being renamed rather than removed.
  • A 756-test suite that stayed green throughout.

Scope and safety

  • Examples are abstract. No corpus content, no personal data.
  • States explicitly that the work is unmerged and that main still ships the previous behaviour, so nothing here reads as a released capability.
  • Includes a "what is not fixed" section.

Draft while the described work is still in progress.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Qw1sMXN1yma2eCi8zZcdpd

…rameters

Records the August measurement work for the public repo. The through-line is
removing magic numbers by letting the data determine its own measurement
parameters, which became necessary on large dense personal corpora and on
opening up organizational use cases.

Covers, with numbers: a distance conversion that was wrong for both Chroma
spaces and that our own architecture doc stated as fact; a faithfulness guard
set below the noise floor of the encoder in use, so it could never fire; a
deduplication step measured at 83% correct when two facts are the same and 23%
when they are not; what that merge behaviour revealed about facts that
disagree; and a 756-test suite that stayed green through all of it.

Examples are abstract. No corpus content. States explicitly that the work is
unmerged and that main still ships the previous behaviour.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qw1sMXN1yma2eCi8zZcdpd
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3a5c54ca-a40f-4f37-a144-975025412322

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

An independent check found three statements in the note stronger than the
evidence behind them:

- The faithfulness guard section said random pairs have a minimum similarity of
  0.358 and that the guard could therefore never fire. That was a sample
  minimum over 600 pairs. Across roughly eight million within-corpus pairs the
  true minimum is 0.276 and about 0.015% fall below 0.35. The guard is
  effectively unreachable for an on-topic English summary, which is what the
  evidence supports.
- The 83% and 23% figures have wide confidence intervals. The direction holds
  (Fisher exact p = 0.001) but the magnitudes are not quotable, so the section
  now leads with the population figure instead.
- Test count 756 to 769.

Also records two limitations of our own method that cut against the
conclusion: the labelling rubric instructed the labeller to be strict about
calling pairs distinct, which biases ground truth toward finding the pipeline
merge-happy, and the harness supplied one candidate neighbour where production
supplies three.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qw1sMXN1yma2eCi8zZcdpd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant